FAQ: How to Get Better at Back End
How to Get Better at Back End
[00:00:00]
This is a lot simpler than it needs to, this doesn't actually have to be hard. The way to get better at back end is to have a problem in your life or have some area where you want to get back time. All you need to do is identify that and then put some back end code there and make a commitment to actually seeing that through.
And seeing it actually now give you back time. You do that, and I am telling you, that's gonna force you to have to learn a lot of different things. Especially if you take that and you turn it into something that's going to be public for other people as well, that's gonna propel you. So in the course there's going to be a section where I ask you to submit a final project.
This is a great scenario. This is a great [00:01:00] opportunity for you to think about a problem like this in your life and write some code to try to solve it. That's a really good one. You can also do this with a community member as well. So there will be some information on that a little bit later on in the course for you to know how to sync up and even find a community member if you want to do that or if you just want to do it by yourself.
But that's gonna give you I would say like a massive level of confidence if you can do that With respect to the phases of craft ship, what are we gonna do? Of course in code first, all we're going to do is just build something out on the back end But you know because everything is on the internet you could look up how to build something with chat GBT it's great and all but we need to take it a little bit further So throughout the phases of craftship in best practice first, we're going to refine this a lot.
We're going to make sure that we can test the back end with an acceptance test. We're going to make sure that we're using a production like environment by using Docker. [00:02:00] And in best practice first, we're going to use a lot of the patterns. And then, of course, in responsibility first, we're going to learn how to actually think.
In terms of responsibilities, roles and collaborations, and then take those things, take those conceptual understandings, do some design, and then actually put them into play, put them into practice in the code based, guided by objects. So I would say those are some of the most impactful ways that you're going to be able to get better at backend.
But something you could just start to think about mull right now is, what problems do I have in my life? What areas do I seem to spend a lot of time that I don't want to spend my time in? Think about those things, and... Start thinking about putting code together for those. You're going to need to do a fair amount of theoretical work up front.
So again, come back to the abstraction prism to know what it is you should be doing at what time. But that's going to give you a massive level of confidence if you can do that for [00:03:00] yourself.